Service Oriented Architecture today can be further expanded by other technologies such as Grid Computing and Smart Clients. Here are some technologies that incorporate Service Oriented Architecture:
\begin{itemize}
\item{\bf Smart Clients:} Smart Clients harness the power of the desktop and couple it with the power of the internet. Thanks to powerful processor companies, like Intel and AMD, Smart Clients can utilize the unused resources and power of the desktop or laptop or any other device and use its internal hardware like memory to accomplish certain tasks. Such tasks can include interaction with software or applications within the device, and when the device is not connected, the smart client can do housekeeping tasks and work on optimizing performance. Smart Clients combined with the Service Oriented Architecture paradigm can enrich the user experience and increase response time with caching and asynchronous data fetching. Smart Clients can interact with web applications and collect data from the Internet if needed. Smart Clients in conjunction with SOA can allow applications to be more robust, flexible and scalable \cite{rajiv}. 
\item{\bf Grid Computing:} Grid Computing is a computing paradigm where computers distributed across a network act as a single virtual entity to distribute and enable parallel computing when possible. As a result, a single virtual computer can solve large complex computational problems by breaking them down into sub tasks and thus enable higher performance. There is no centralized control and computation is distributed. The computers in the grid are also geographically distributed which makes interoperable communications difficult. Following SOA's interoperability paradigm, the computers in the grid must use standardized protocols and interfaces to enable interoperability among heterogeneous machines and optimize performance through efficient use of available resources \cite{rajiv}. 
\item{\bf M2M (Machine-to-Machine):}Machine-to-machine technologies are involved in bringing online machines and peripherals of everyday use and have devices interact with both wired and wireless systems. It raises the possibility of connecting such devices to intranets and internet, to enable monitoring of performance, receiving alerts on critical entities, and to control and manipulate them. The system that the devices interact with can collect meaningful data such as temperature, quality level, pressure, and other characteristics. An example of Machine-to-Machine technology can be a water purification monitoring system. There can be devices setup throughout the water purification system and those devices can send data to the main system such as the quality of the water \cite{rajiv}.
\end{itemize}

\subsection{SOA in Current Technologies}

Regardless of whether or not SOA will continue to exist in the future, the principles of  SOA will still be around as long as it is survived by other technologies, such as:
\begin{itemize}
\item{\bf Web Services}: Web Services, as mentioned in the History section, can be implemented with SOA. If one compares figures 1 and 2, it can be seen that Web Services can follow SOA structure where the service provider registers their services in the service directory so that clients are able to find and use those services after agreeing to a service contract and given an endpoint to the address. Much like SOA, Web Services support interoperable machine to machine communication through a network to enable communications among the client, service provider, and service directory \cite{qusay}.
\item{\bf Cloud Computing}: Cloud Computing allows consumers to use applications without installation or knowledge of how the application works. It is a computing structure that hosts software services over the Internet to customers in the form of a ``cloud.'' Many email softwares like Gmail are hosted in the cloud. Both Cloud Computing and SOA emphasize the importance of services and loose coupling to enable business functionality and system independence \cite{jamil}.
\item{\bf Software as a Service (SaaS)}: SaaS and SOA are often thought to be the same but they are not. SaaS is basically a term that means ``hosting a set of software services over the Web.'' The difference between SaaS and SOA is that SaaS means Software Hosted as a Service while SOA means Software designed as a Service. However, both stress the principle of services but both are different in that SaaS is a way of delivering a service while SOA is a way of how a service is delivered. Nevertheless, SaaS follows SOA's interoperability principle to enable communications between the client side application and the server side software \cite{jamil}.
\end{itemize}

\subsection{SOA 2.0: Event Driven SOA}
There is also a lot of buzz about SOA 2.0. SOA 2.0 combines service oriented architecture with event driven architecture. Instead of having services being triggered by a business process, services can be triggered through random or scheduled events. Hospital systems, bank systems, and other processing systems can have services act as alerts or notifications to better serve consumers or clients. Although many do not feel that this advanced version of SOA deserves the attached version number 2.0, this future direction for SOA still has potential to grow into a popular architectural style \cite{hanson}. 